Improve Settings Reference documentation and fix python-env.* naming inconsistency#1114
Merged
StellaHuang95 merged 3 commits intomicrosoft:mainfrom Jan 30, 2026
Merged
Conversation
anthonykim1
reviewed
Jan 30, 2026
anthonykim1
reviewed
Jan 30, 2026
eleanorjboyd
approved these changes
Jan 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR does the following:
Renames
python-env.*settings topython-envs.*for consistency and updatespackage.json, localization files, and source code accordingly.Restructures the settings tables for clarity, adds missing documentation for Python Environments settings, and clarifies supported values and path resolution behavior.
Improves user-facing guidance on legacy Python settings, including migration paths and deprecation notes, and documents the planned replacement of terminal activation settings with
python-envs.terminal.autoActivationTypebased on discussion with Anthony.Here's what the readme looks like now.
